Data collection policy for storage devices

ABSTRACT

Collecting data for a storage area network includes providing a plurality of agents that collect data from objects of the storage area network, providing a plurality of data collection policies, where each of the policies indicates a type of data to be collected and a frequency of collection, and applying the policies to the agents, where the agents collect data according to the type of data and the frequencies indicated by the data collection policies. At least one of the agents may have a plurality of data collection policies applied thereto to cause the at least one agent to collect the types of data at the frequencies indicated by the merge of all of the data collection policies applied to the at least one agent. Merging the data collection policies may be performed by the at least one of the agents that receives the data collection policies or may be performed by an entity other than the at least one of the agents.

BACKGROUND OF THE INVENTION

1. Technical Field

This application relates to the field of computer storage devices, andmore particularly to the field of monitoring and controlling operationof objects in a system containing storage devices.

2. Description of Related Art

Host processor systems may store and retrieve data using a storagedevice containing a plurality of host interface units (host adapters),disk drives, and disk interface units (disk adapters). Such storagedevices are provided, for example, by EMC Corporation of Hopkinton,Mass. and disclosed in U.S. Pat. No. 5,206,939 to Yanai et al., U.S.Pat. No. 5,778,394 to Galtzur et al., U.S. Pat. No. 5,845,147 toVishlitzky et al., and U.S. Pat. No. 5,857,208 to Ofek. The host systemsaccess the storage device through a plurality of channels providedtherewith. Host systems provide data and access control informationthrough the channels to the storage device and the storage deviceprovides data to the host systems also through the channels. The hostsystems do not address the disk drives of the storage device directly,but rather, access what appears to the host systems as a plurality oflogical disk units. The logical disk units may or may nor correspond tothe actual disk drives. Allowing multiple host systems to access thesingle storage device unit allows the host systems to share data storedtherein.

A large system may consist of a plurality of hosts, a plurality ofstorage devices, and a plurality of switches that direct data betweenthe hosts and the storage devices. Such a system, called a storage areanetwork (SAN), provides for certain efficiencies and optimizations whenthe storage devices and hosts are used together. However, it may bedifficult to monitor and control the objects of the SAN. One solution tothis is to use special software provided by EMC Corporation ofHopkinton, Mass. for monitoring and controlling the objects. The EMCsoftware runs on one or more hosts to monitor the SAN. The software alsoincludes agents, which are separate programs that collect data from eachof the objects of the SAN and report back to the EMC software running onthe one or more hosts.

The agents used with the EMC software may be customized for each objectand application. Thus, the data collection frequencies and type of datacollected may be “built in” for each of the agents. However, in somecases, a user of the EMC software may want to change the frequency andtype of data collected. A user may also want to standardize datacollection across groups of objects or across objects of like type.However, with the data collection information built into the agents, itmay be difficult for a user to change the frequency or type of datacollected by the agents. Accordingly, it is desirable to provide amechanism for modifying the data collection of the agents by a user ofthe EMC software.

SUMMARY OF THE INVENTION

According to the present invention, collecting data for a storage areanetwork includes providing a plurality of agents that collect data fromobjects of the storage area network, providing a plurality of datacollection policies, where each of the policies indicates a type of datato be collected and a frequency of collection, and applying the policiesto the agents, where the agents collect data according to the type ofdata and the frequencies indicated by the data collection policies. Atleast one of the agents may have a plurality of data collection policiesapplied thereto to cause the at least one agent to collect the types ofdata at the frequencies indicated by the merge of all of the datacollection policies applied to the at least one agent. Merging the datacollection policies may be performed by the at least one of the agentsthat receives the data collection policies. Merging the data collectionpolicies may be performed by an entity other than the at least one ofthe agents. Collecting data for a storage area network may includedisplaying to a user at least one of the data collection policies for atleast one of the agents. Collecting data for a storage area network mayinclude allowing the user to modify the at least one data collectionpolicy for the at least one of the agents. Collecting data for a storagearea network may include, in response to a user modifying the at leastone data collection policy, providing the at least one data collectionpolicy to the at least one agent. Allowing a user to modify the at leastone data collection policy may include allowing a user to delete the atleast one data collection policy. Collecting data for a storage areanetwork may include, in response to a user modifying the at least onedata collection policy, providing to the at least one agent all of thedata collection policies for the at least one agent. Allowing the userto modify the at least one data collection policy may include allowingthe user to select one or more of the agents to which the at least onedata collection policy is to be applied. The user may be restricted toapplying the at least one data collection policy to only agents of anappropriate type. Allowing the user to modify the at least one datacollection policy may include having the user modify a template for theat least one data collection policy. Applying the policies to the agentsmay override any of the agents' built-in data collection policies. Eachof the data collection policies may be applied to a single agent, agroup of agents, or agents that service a particular type of object ofthe storage area network. Collecting data for a storage area network mayinclude at least one of the agents maintaining a local copy of the datacollection policies applied thereto.

According further to the present invention, computer software thatcollects data for a storage area network includes a plurality ofexecutable code software agents that collect data from objects of thestorage area network, executable code that manages a plurality of datacollection policies, where each of the policies indicates a type of datato be collected and a frequency of collection, and executable code thatapplies the policies to the agents, where the agents collect dataaccording to the type of data and the frequencies indicated by the datacollection policies. At least one of the agents may have a plurality ofdata collection policies applied thereto to cause the at least one agentto collect the types of data at the frequencies indicated by the mergeof all of the data collection policies applied to the at least oneagent. At least one of the agents may include executable code to mergethe data collection policies applied thereto. Computer software thatcollects data for a storage area network may also include executablecode to display to a user at least one of the data collection policiesfor at least one of the agents. Computer software that collects data fora storage area network may also include executable code to allow theuser to modify the at least one data collection policy for the at leastone of the agents. Computer software that collects data for a storagearea network may also include executable code that provides the at leastone data collection policy to the at least one agent in response to auser modifying the at least one data collection policy. Computersoftware that collects data for a storage area network may also includeexecutable code that allows a user to delete the at least one datacollection policy. Computer software that collects data for a storagearea network may also include executable code that provides to the atleast one agent all of the data collection policies for the at least oneagent in response to a user modifying the at least one data collectionpolicy. Computer software that collects data for a storage area networkmay also include executable code that allows the user to select one ormore of the agents to which the at least one data collection policy isto be applied. Computer software that collects data for a storage areanetwork may also include executable code that restricts the user toapplying the at least one data collection policy to only agents of anappropriate type. Computer software that collects data for a storagearea network may also include executable code that facilitates the usermodify a template for the at least one data collection policy. Theagents may include executable code that overrides any of the agents'built-in data collection policies. Computer software that collects datafor a storage area network may also include executable code for applyingeach of the data collection policies to a single agent, a group ofagents, or agents that service a particular type of object of thestorage area network.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a storage area network (SAN) thatcontains a plurality of hosts, a plurality of storage devices, and aplurality of switches according to the system described herein.

FIG. 2 is a screen display showing an aspect of using a program tomonitor and control a SAN according to the system described herein.

FIG. 3 shows an expanded menu for a screen display for a program tomonitor and control a SAN according to the system described herein.

FIG. 4 shows a further expanded portion of the menu of FIG. 3 accordingto the system described herein.

FIG. 5 shows a pull down menu used in connection with selecting an itemaccording to the system described herein.

FIG. 6 shows a dialog box for editing properties of a data collectionpolicy template for an agent according to the system described herein.

FIG. 7 shows a dialog box for creating a new data collection policyinstance for an agent according to the system described herein.

FIG. 8 shows a further expanded portion of the menu of FIG. 3 accordingto the system described herein

FIG. 9 shows a pull down menu used in connection with selecting an itemaccording to the system described herein.

FIG. 10 shows a dialog box for determining if a user intends to delete aparticular data collection policy according to the system describedherein.

FIG. 11 shows a dialog box for applying a data collection policy to oneor more particular agents according to the system described herein.

FIG. 12 shows a dialog box for choosing a source of data collected for adata collection policy according to the system described herein.

FIG. 13 shows a dialog box for choosing frequency of collection actionsthat may be selected for data collection policy according to the systemdescribed herein.

FIG. 14 shows a dialog box for applying a data collection policy to oneor more particular agents according to the system described herein.

FIG. 15 is a block diagram illustrating a relationship between portionsof a program used to monitor and control operation of a SAN according tothe system described herein.

FIG. 16 is a diagram showing a relationship between data used inconnection with data collection policies according to the systemdescribed herein.

FIGS. 17A and 17B are a flow charts illustrating operation of a serverportion of a program used to monitor and control operation of a SANaccording to the system described herein.

FIG. 18 is a diagram illustrating a table used to store information foragents that monitor objects in a program used to monitor and controloperation of a SAN according to the system described herein.

FIG. 19 is a flow chart illustrating a portion of initialization of aprogram used to monitor and control operation of a SAN according to thesystem described herein.

FIG. 20 is a flow chart illustrating steps for handling failure of anagent of a program used to monitor and control operation of a SANaccording to the system described herein.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Referring to FIG. 1, storage area network (SAN) 30 includes a pluralityof hosts 32-34, coupled to a plurality of storage devices 36-38 via aSAN fabric 42. The SAN fabric 42 may include a plurality of switches44-46 that switch data between the hosts 32-34 and the storage devices36-38. The SAN fabric 42 may connect one or more of the hosts 32-34 toone or more of the storage devices 36-38 via one or more of the switches44-46. A system for monitoring and configuring a SAN 30 is disclosed,for example, in U.S. patent application Ser. No. 09/431,758 filed onNov. 1, 1999, which is incorporated by reference herein. The followingdiscussion relates to that type of system that may be used inconjunction with, or as a supplement to, the system disclosed in U.S.patent application Ser. No. 09/431,758.

It is possible to have a program running on one or more of the hosts32-34 to monitor operation of one or more objects that are components ofthe SAN 30, such as the hosts 32-34, the storage devices 36-38, and/orthe switches 44-46. The program includes subprograms/tasks called“agents”, which run independently to monitor information on an object(e.g., one of the storage devices 36-38, one of the switches 44-46, oneof the hosts 32-34, etc.) and transfer data about the objects as well asreceive data indicating what should be monitored and how often. Eachagent is written specifically for the type of object it monitors and thedata it collects. However, as explained in detail elsewhere herein, itis possible to generically specify the data collection policies(object/frequency/type of data) for the agents. In some cases, theagents may have been provided with built in data collection policieswhich may be either overridden or “merged” (described below) with thegenerically specified and dynamic data collection policies describedherein.

Referring to FIG. 2 the program to monitor and control the SAN 30provides a screen 50 to a user of the program. The screen 50 includes afolder tree 51 that has a plurality of folders and related items thatfacilitate monitoring and controlling the SAN 30. One of the folders 52relates to data collection policies. Inside the folder 52 is a subfolderfor policy definitions 54 and a subfolder for policy templates 56. Thedata collection policy definitions represented by the folder 54 relatesto the actual data collection policies for each of the agents used onthe system. As explained in more detail elsewhere herein, it is possibleto modify the actual data collection policy for one or more individualagents, one or more groups of agents, and/or one or more types of agentsor types of objects monitored by the agents. For example, it may bepossible to modify the data collection policy definitions applied to allstorage devices in the system. As explained in more detail elsewhereherein, such a modification would affect agents that perform datacollection on storage devices. Similarly, it is possible to have groupsof agents, such as a group of agents relating to a particular type ofstorage device (e.g., Symmetrix storage devices provided by EMCCorporation of Hopkinton, Mass.). In such a case, it may be possible tomodify the data collection policies of only those agents that belong tothe group, in which case a modification would affect all agentscorresponding to the group. Agents may belong to more than one group. Itis also possible to modify the data collection policy of a specificagent.

Note further that it is possible for an agent to have more than one datacollection policy applied thereto. In that case, all of the datacollection policies for a particular agent are merged (OR'ed) to causethe agent to collect data according to all of the policies which apply.Thus, for example, if an agent is subject to a first policy that causesdata collection on Monday, Wednesday, and Friday, and a second policythat causes data collection on Tuesday, Thursday, Saturday, and Sunday,that agent will collect data every day of the week according to onepolicy or the other. In some embodiments, it is possible to display alist of agents and right click on each agent to show that applicabledata collection policies. The merging may be performed by the agents orby an other entity, such as the entity that provides data collectionpolicy information to the agents.

The data collection policy templates folder 56 represents generictemplates for different types of objects. Thus, unlike the datacollection policy definitions folder 54, which contains actual policydefinitions for agents in the system, the data collection policytemplates folder 56 corresponds to data collection policy templateswhich are not applied to any specific agents but which may be used inconnection with creating and/or editing data collection policydefinitions for agents.

Referring to FIG. 3, a screen 60 illustrates expansion of the datacollection policy templates folder 56 to show a plurality of items 62that correspond to specific types of templates. As explained in moredetail elsewhere herein, each of the items 62 may be further expanded toshow specific templates. In some embodiments, expansion/selection ofitems may be provided by right clicking the mouse.

Referring to FIG. 4, one of the items 62 corresponding to the databaseagents for Oracle is shown as expanded into four separate items 64-67.Each of the items 64-67 corresponds to a particular type of templatethat may be used to monitor a database for Oracle. A user may select oneof the particular types corresponding to the items 64-67 to performediting and/or to create an instance of a data collection policy for anOracle agent.

Referring to FIG. 5, a pull down menu 68 is provided when a user selectsthe item 65 that is contained in the database agents for oracle folder62. The menu 68 includes selections for properties, copy, new, edit, andothers. Selecting the properties from the menu 68 allows a user to viewthe properties of the data collection policy template. Selecting copyfrom the menu 68 allows the user to copy the template. Selecting newfrom the menu 68 allows the user to create a new instance of thetemplate. Selecting edit from the menu 68 allows the user to edit thetemplate. The result of selecting different menu options is discussed inmore detail elsewhere herein.

Referring to FIG. 6, a dialog box 70 is provided in connection with theuser selecting edit from the menu 68 of FIG. 5. The dialog box includesa properties tab 72, which is shown in FIG. 6 as being the selected tab.The information in the dialog box 70 includes an agent identificationfield 74, a template name field 75, a last modified field 76, and a whomodified field 77. The dialog box 70 may also include a description 78that could aide a user in connection with using the data collectionpolicy template.

Referring to FIG. 7, a dialog box 80 is provided in connection with auser selecting the new item from the menu 68 of FIG. 5. The dialog box80 includes a properties tab 82 (which is selected), an agent field 84,a template name field 85, a last modified field 86, and a who modifiedfield 87. The dialog box 80 also contains a description field 88. Notethat the dialog box 80 is similar to the dialog box 70 of FIG. 6.However, the dialog box 80 allows a user to create a new data collectionpolicy instance to be applied to an agent in a manner describedelsewhere herein. In contrast, the dialog box 70 simply allows a user toedit an existing data collection policy template.

Referring to FIG. 8, a portion of FIG. 3 is shown where an itemcorresponding to the specific data collection policy 52 is expanded.Unlike the data collection templates, which do not apply to any specificagents, each of the items in the data collection policies folder 54corresponds to a specific policy for one or more specific agents. Thedata collection policies folder 54 contains a plurality of subfolders92-95 which correspond to different groups of agents. Each of thesubfolders 92-95 contains items corresponding to specific agents forobjects of the storage area network being monitored and controlled.Thus, for example, the subfolder 93 may be expanded to show a pluralityof items 96, each of which corresponds to a data collection policy for aspecific agent.

Referring to FIG. 9, a menu 98 is provided when a user selects one ofthe items 96. The menu 98 includes a properties, copy, and edit choicessimilar to the menu 68 of FIG. 5, discussed above. A “copy as” selectionallows a user to copy the specific data collection policy but change thename. In contrast, the “copy” selection automatically changes the nameonly slightly. The delete option allows deletion of the data collectionpolicy. The add/remove object, described below, allows for the additionor removal of objects. Selecting disable from the menu 98 prevents thepolicy from operating on the agent.

Referring to FIG. 10, a dialog box 102 illustrates what is provided inconnection with the user selecting delete from the menu 98 of FIG. 9.The dialog box 102 allows a user to confirm deletion of the datacollection policy. As described elsewhere herein, once a data collectionpolicy is deleted, agents that use the policy will be informed and willno longer collect data according to the policy.

Referring to FIG. 11, a dialog box 104 is provided in connection with auser selecting add/remove object from the menu 98 of FIG. 9. Note thatthe dialog box 104 may also be provided in connection with the userselecting an Apply To tab 106 in the dialog box 80 of FIG. 7. Thus, thedialog box 104 may be reached either by the user selecting add/removeobject from the menu 98 or by the user selecting the apply to tab in thedialog box 80.

The dialog box 104 allows a user to apply the specific data collectionpolicy to one or more specific agents, one or more specific groups ofagents/objects, and/or one or more specific types of agents/objects. Thefollow on processing that is performed once the data collection policiesfor one or more agents have been modified is described in more detailelsewhere herein.

Referring to FIG. 12, a dialog box 112 is provided in connection with auser selecting a Source tab 114 in a policy definitions dialog box likethe dialog box 80 of FIG. 7 and the dialog box 104 of FIG. 11. Thedialog box 112 allows a user to select a source of data (i.e., the typeof data that is collected). For each different type of agent and datacollection policy, the dialog box 112 will be different because the typeof data that may be collected and/or may be desirable to collect may bedifferent for different types of agents and different types of objects.

Referring to FIG. 13, a dialog box 122 is provided in connection withselecting the Actions tab 124 of a dialog box like the dialog box 112 ofFIG. 12, the dialog box 104 of FIG. 11, and the dialog box 80 of FIG. 7.The dialog box 122 allows a user to select the frequency of datacollection for the particular data collection policy. The differentoptions on the dialog box 122 allow collection of data at differentintervals.

Referring to FIG. 14, a dialog box 132 is provided in connection withselecting an Apply To tab 134 on a dialog box like the dialog box 122 ofFIG. 13, the dialog box 112 of FIG. 12, and the dialog box 80 of FIG. 7.The dialog box 132 allows a user to select an agent, group ofagents/objects, and/or type of agent/object to apply the particular datacollection policy. A field 133 of the dialog box 132 indicates thepossible choices to which the data collection policy may be applied.Note that the choices for applying the data collection policy arelimited to the type of agent that corresponds to the data collectionpolicy. Thus, in the example of FIG. 14, only the databases item 136 isselectable in the window on the left hand side while all of the otheritems, such as the device groups item 138, are not selectable. Thisprevents a user from applying a data collection policy to aninappropriate agent.

Use of generic data collection policies across different types of agentsas described herein allows for centralized management of data collectionpolicies for the agents. The data collection policies also allowstandardization of data collection across different objects of a storagearea network.

Referring to FIG. 15, a diagram 180 illustrates a structure of a programto monitor and control objects associated with a storage area network.The program includes a console module 182, a server module 184, and adatabase module 186 that contains a data collection policy data element188. The program also includes a plurality of store modules 192 and aplurality of agents 194. Each of the modules 182, 184, 186, 192, 194 mayor may not reside on the same or different objects associated with thestorage area network. The console 182, the server 184, the database 186,and the store modules 192 may reside on one or more hosts. Each of theagents 194 may reside on the particular object for which the agent isresponsible or, in some instances, may reside on an object where theagent has appropriate access to the data being collected for the object.For example, an agent collecting data related to a particular storagedevice may reside on a host coupled to that storage device provided thatthe agent is able to obtain the information that it needs about thestorage device from the host.

The interconnections between the modules 182, 184, 186, 192, 194illustrate data paths therebetween. Thus, for example, there is atwo-way data path between the console 182 and the server 184. Asdescribed elsewhere herein, in some instances it may not be necessaryfor a data path to be persistent, provided that the data path isavailable when data needs to be communicated. In some instances, dataneeds to be communicated at certain times and not at others.

The console 182 represents the portion of the program that interactswith a user. Thus, the console 182 provides the screens and menus to theuser described herein. The console 182 also receives input from the userwho makes selections and/or edits as described elsewhere herein. Thusthe console 182 is, in effect, the user interface for the remainder ofthe program. The console 182 may be implemented using Java and standardsystem calls to provide the user interface.

The database 186 includes the data collection policy data element 188that represents the data collection policies and the data collectiontemplates that apply to all of the agents 194. In other embodiments, thedata collection policy data element 188 may be stored separate orpartially separate from the database 186. The data collection policydata element 188 may also be distributed among more than one host and/orother device.

When a user edits a data collection policy or a data collection policytemplate, the specific data for the policy/template being modified isprovided by the database 186 from the data collection policy dataelement 188 to the console 182 through the server 184. In otherembodiments, data from the data collection policy data element 188 maybe provided directly from the database 186 to the console 182 withoutfirst passing through the server 184. The direct communication may beused to enhance performance. Note that the database 186, the server 184,and the console 182 may be on different hosts or may be on the samehost, or some combination thereof. In any event, when a user edits thedata for a data collection policy or a data collection policy template,the initial data presented to the user by the console 182 is providedfrom the data collection policy data element 188.

After the data has been modified by the user, the console 182 providesthe data to the server 184 which pushes the data back to the database186 for storage in the data collection policy data element 188. Theserver also determines which, if any, of the agents 194 need to receivethe new data collection policy. Note that, in some instances, a user'sedits may only relate to data collection policy templates, in which casethe server 184 may simply provide the data back to the database 186 forwriting to the data collection policy data element 188. However, ininstances where modifications by a user require propagation to theagents 194, the server 184 determines which agents require the new dataand will provide the new data collection policy to the agents 194.Thereafter, each of the agents 194 collect data and provide the data toone of the store modules 192 which then may store the data to thedatabase 186.

In some embodiments, one or more of the agents 194 may maintain a localcopy of its data collection policy. Thus, in some instances, the agents194 may continue to collect data without requiring a persistentconnection between the server 184 and the agents 194. In someembodiments, the agents 194 poll the server 184 prior to each collectionof data. The server 184 indicates to the agents 194 the identity of aparticular one of the store modules 192 to which the data should beprovided by the agents 194. The server 184 may select the particular oneof the store modules 192 based on a variety of functional factorsobvious to one skilled in the art, such as load balancing. Theparticular one of the store modules 192 may then transfer the collecteddata to the database 186. In some embodiments, there may be only onestore module which may be used to receive data from the agents 194.

Referring to FIG. 16, the data collection policy data element 188includes a data collection policy templates 202, data collection policyinstances 204, and control groups 206. The control groups 206 containinformation regarding the frequency of data collection. Each of the datacollection policy templates 202 and data collection policy instances 204may contain a pointer to an entry in the control groups 206 to indicatethe frequency of data collection. The information in the data collectionpolicy templates 202 and data collection policy instances 204corresponds to the other data collection policy information discussedelsewhere herein.

The data may be stored in any appropriate fashion, includingconventional tables. The data collection policy tables may contain aname field, a list of possible sources of data (see on the Source tab,described above), help information (used if the user selects help), andinformation indicating the type of object/agent to which the datacollection policy applies. The tables may also include a fieldindicating whether the type of data collection policy is uniquelyassigned to an agent (preventing other data collection policies of thesame type being assigned to the same agent), a field indicating whetherthe data collection policy is enabled or disabled, a description of thedata collection policy (described above), a pointer to the appropriatecontrol group for, the data collection policy, an indicator of whetherthe data collection policy is assigned to all types of objects to whichit applies, a field indicating the date of last modification of the datacollection policy, and a field indicating the user that made the lastmodification.

Referring to FIG. 17A, a flow chart 250 illustrates steps performed bythe server 184 after a user defines a new control group or changes anexisting control group definition. Processing begins at a first step252, where the server 184 receives the new information from the console182. As discussed elsewhere herein, the console 182 provides a userinterface to display and receive data, including data about datacollection policies. The console 182 and the server 184 may reside onthe same host or on different hosts. The communication between theconsole 182 and the server 184 may be by any appropriate means suitableto provide the functionality described herein.

Following the step 252 is a step 254 where the new information receivedat the step 252 is passed to the database 186 for storing in the datacollection policy data element 188. As discussed elsewhere herein, thedatabase 186 and the server 184 may be provided on the same host or ondifferent hosts. In addition, just as with the console 182 and theserver 184, the communication between the database 186 and the server184 may be by any appropriate means suitable to provide thefunctionality described herein. The data passed from the server 184 tothe database 186 is stored in the data collection policy data element188 for follow on processing as described elsewhere herein.

Following the step 254 is a step 256 where the server 184 pushes newcontrol group information to the affected ones of the agents 194.Following the step 256 is a step 258 where the server 184 acknowledgesto the console 182 that the server 184 has completed processing the useredits passed from the console 182 to the server 184 at the step 252. Thestep 258 may be eliminated or may be optional in some embodiments.

Referring to FIG. 17B, a flow chart 260 illustrates steps performed bythe server 184 after a user changes a data collection policy for one ormore agents. Processing begins at a first step 262, where the server 184receives the new information from the console 182. As discussedelsewhere herein, the console 182 provides a user interface to displayand receive data, including data about data collection policies. Theconsole 182 and the server 184 may reside on the same host or ondifferent hosts. The communication between the console 182 and theserver 184 may be by any appropriate means suitable to provide thefunctionality described herein.

Following the step 262 is a step 264 where the new information receivedat the step 262 is passed to the database 186 for storing in the datacollection policy data element 188. As discussed elsewhere herein, thedatabase 186 and the server 184 may be provided on the same host or ondifferent hosts. In addition, just as with the console 182 and theserver 184, the communication between the database 186 and the server184 may be by any appropriate means suitable to provide thefunctionality described herein. The data passed from the server 184 tothe database 186 is stored in the data collection policy data element188 for follow on processing as described elsewhere herein.

Following the step 264 is a test step 266, where it is determined if anyof the passed information affects any of the agents 194. As discussedelsewhere herein, user edits may or may not affect actual datacollection policies of one or more of the agents 194. If it isdetermined at the step 266 that one or more of the agents 194 has beenaffected, then control passes from the step 266 to a step 268, where thenew data collection policy information is pushed from the server 184 tothe affected ones of the agents 194. Note that at the step 268, it ispossible to provide each affected agent with all of the agent's datacollection policies, including policies that have not changed. Thus, forexample, if a particular agent has ten applicable data collectionpolicies (which are merged, as described elsewhere herein), the server184 could send all ten to the particular agent, even though not all havebeen changed by user edits. Note also that, in some embodiments, theserver 184 could first merge the applicable data collection policies andthen send the results of the merge to the agents.

A step 272 follows the step 266 or the step 268. At the step 268, theserver 184 acknowledges to the console 182 that the server 184 hascompleted processing the user edits passed from the console 182 to theserver 184 at the step 262. The step 272 may be eliminated or beoptional in some embodiments.

In some cases, a user may want to initiate or adjust monitoring aparticular object in the SAN 30, but may not know which agents areresponsible for the particular object. In those cases, it would beuseful to have a mechanism that allows a user to specify a particularobject (or group of objects or type of object) rather than having toknow the identity of an agent. In addition, in some cases it is possiblefor an agent to stop working for any number of reasons. When thishappens, it would be useful to have an automatic mechanism for providinga different agent to take over the data collection of the failed agent.

Referring to FIG. 18, a table 280 includes a plurality of entries282-284, each of which corresponds to an element of the SAN 30. Thetable 280 may be part of the data collection policy data element 188,discussed above. The table 280 may be accessed and/or modified by theserver 184 through the database 186. In other embodiments, the table 280may be stored separate from the data collection policy data element 188and may also be separate or partially separate from the database 186.The table 280 may also be distributed among more than one host and/orother device.

The table 280 includes a plurality of elements 282-284, each of whichmay represent, for example, an object or specific data to be monitored.Each of the elements 282-284 has three fields. The first fieldcorresponds to an element identifier 282′-284′. The second fieldcorresponds to an operation identifier 282″-284″. The third fieldcorresponds to an agent information field 282′″-284′″. The elementidentifier fields 282′-284′ identify each of the elements. For example,an element may be identified as a particular storage device. Theoperation identifiers 282″-284″ represent operations that may beperformed for each of the corresponding elements. For example, if theelement identifier 282′ corresponds to a particular storage device, thenthe operation 282″ could, for example, correspond to monitoring aparticular statistic for the particular storage device. The agentinformation fields 282′″-284′″ indicates a specific agent for providingthe corresponding operation to the corresponding element. The agentinformation fields 282′″-284′″ also include an indication of whether theagent is a primary or secondary (described below) and the cost of usingthe agent (described below).

Using the table 280, a user could specify a particular object (and aparticular statistic of the object) to be monitored. The server 184could then use the table 280 to find an appropriate entry having amatching element and operation. The agent indicated by the agent infofield of that entry would be the agent used to monitor the objectspecified by the user.

Referring to FIG. 19, a flow chart 300 illustrates steps performed inconnection initializing the table 280 of FIG. 18. The steps of the flowchart 300 may be performed when the system is initialized/installed.Processing begins at a first step 302 where the agents are installed.Following the first step 302 is a second step 304 where the serverreceives information from the newly installed agents. The informationthat the server receives from each of the agents includes an identifierfor the agent along with data indicating what the agent is capable ofmonitoring.

Following step 304 is a step 306 where the table entry for theinformation received by each of the agents is created. As discussedabove, each entry in the table 280 includes an element identifier, anoperation identifier, and agent information. The element and operationmay correspond to the information received at the step 304. Similarly,the agent identifier field may include the information received at thestep 304. An indication of whether the agent is a primary or secondarymay be provided in connection with user-defined configurationparameters. Alternatively, an algorithm may be used to determinedynamically whether an agent is a primary or secondary agent. Forexample, the algorithm could indicate that the first element that isreceived for performing a particular operation is deemed the primarywhile all other information received corresponding to the same elementand operation will be deemed secondary. Other algorithms may also beused.

Also provided at the step 306 is the information in the table entryrelated to the cost for using the agent. The cost may be a quantity thatis used when the agent is promoted from a secondary to a primary todetermine which agent to promote from secondary to primary. The cost maybe determined using any reasonable heuristic, such as determining theamount of processing time required for the agent to perform theoperation for the element indicated by the table entry. Other means fordetermining cost may also be used. In any event, the cost is provided inthe table entry created at the step 306.

Following the step 306 is a test step 308 which determines if there ismore data being provided from more agents. If not, then processing iscomplete. Otherwise, control passes from a step 308 back to the step304, to continue processing, as discussed above.

Referring to FIG. 20, a flow chart 320 illustrates steps performed inconnection with failure of a primary agent and promotion of a secondaryagent to a primary agent. Processing begins at a first step 322 wherethe server 184 checks to see if any of the primary agents have failed.The check at the step 322 may be performed by any one of a variety ofmechanisms, including polling each of the agents and receiving statusinformation back from the agents indicating health or, in the event thatan agent does not respond, determining that the agent has failed.Following the step 322 is a test step 324 which determines if any agentshave failed. If not, then processing is complete. Note that steps of theflow chart 320 may be run by the server 184 periodically to determine ifany agents have failed.

If it is determined at the test step 322 that a particular agent hasfailed, control passes from the step 324 to a step 326 where the server184 sends notification information to processes and/or objects that areto be notified that the agent has failed. For example, if the primaryagent runs on a particular storage device, the storage device may benotified that the agent has failed. Similarly, the database 186 maycontain configuration information which may need to be adjusted inconnection with the agent failing.

Following the step 326 is a step 328 where the table 280 is recalculatedto reflect that a primary agent has been eliminated. Part of therecalculation includes promoting one of the secondary agents to aprimary agent. As discussed above, this may be performed by selectingthe secondary agent that performs the same operation on the same elementand has the lowest cost relative to other similar secondary agents. Oncethe table 280 has been recalculated, control passes from a step 328 to astep 322 where the new data from the table 280 is provided to each ofthe objects and/or processes that require the information. For example,the object that was monitored by the failed primary agent may benotified at the step 332. In addition, the database 186 may containconfiguration data that needs to be modified in connection withrecalculation of the table 280 at the step 328. Following the step 332,control passes back to the step 322 to receive more failure information(if necessary) followed by the step 324 to determine if any other agentshave failed, as discussed above.

While the invention has been disclosed in connection with variousembodiments, modifications thereon will be readily apparent to thoseskilled in the art. Accordingly, the spirit and scope of the inventionis set forth in the following claims.

1. A method of collecting data for a storage area network, comprising:providing a plurality of agents that collect data from objects of thestorage area network; providing a plurality of data collection policies,wherein each of the policies indicates a type of data to be collectedand a frequency of collection; and applying the policies to the agents,whereby the agents collect data according to the type of data and thefrequencies indicated by the data collection policies, wherein at leastone of the agents has a plurality of data collection policies appliedthereto to cause the at least one agent to collect the types of data atthe frequencies indicated by the merge of all of the data collectionpolicies applied to the at least one agent.
 2. A method, according toclaim 1, wherein merging the data collection policies is performed bythe at least one of the agents that receives the data collectionpolicies.
 3. A method, according to claim 1, wherein merging the datacollection policies is performed by an entity other than the at leastone of the agents.
 4. A method, according to claim 1, furthercomprising: displaying to a user at least one of the data collectionpolicies for at least one of the agents.
 5. A method, according to claim4, further comprising: allowing the user to modify the at least one datacollection policy for the at least one of the agents.
 6. A method,according to claim 5, further comprising: in response to a usermodifying the at least one data collection policy, providing the atleast one data collection policy to the at least one agent.
 7. A method,according to claim 6, wherein allowing a user to modify the at least onedata collection policy includes allowing a user to delete the at leastone data collection policy.
 8. A method, according to claim 5, furthercomprising: in response to a user modifying the at least one datacollection policy, providing to the at least one agent all of the datacollection policies for the at least one agent.
 9. A method, accordingto claim 5, wherein allowing the user to modify the at least one datacollection policy includes allowing the user to select one or more ofthe agents to which the at least one data collection policy is to beapplied.
 10. A method, according to claim 9, wherein the user isrestricted to applying the at least one data collection policy to onlyagents of an appropriate type.
 11. A method, according to claim 5,wherein allowing the user to modify the at least one data collectionpolicy includes having the user modify a template for the at least onedata collection policy.
 12. A method, according to claim 1, whereinapplying the policies to the agents overrides any of the agents'built-in data collection policies.
 13. A method, according to claim 1,wherein each of the data collection policies are applicable to a singleagent, a group of agents, or agents that service a particular type ofobject of the storage area network.
 14. A method, according to claim 1,further comprising: at least one of the agents maintaining a local copyof the data collection policies applied thereto.
 15. Computer software,stored in a computer-readable medium, that collects data for a storagearea network, comprising: a plurality of executable code software agentsthat collect data from objects of the storage area network; executablecode that manages a plurality of data collection policies, wherein eachof the policies indicates a type of data to be collected and a frequencyof collection; and executable code that applies the policies to theagents, whereby the agents collect data according to the type of dataand the frequencies indicated by the data collection policies, whereinat least one of the agents has a plurality of data collection policiesapplied thereto to cause the at least one agent to collect the types ofdata at the frequencies indicated by the merge of all of the datacollection policies applied to the at least one agent.
 16. Computersoftware, according to claim 15, wherein at least one of the agentsincludes executable code to merge the data collection policies appliedthereto.
 17. Computer software, according to claim 15, furthercomprising: executable code to display to a user at least one of thedata collection policies for at least one of the agents.
 18. Computersoftware, according to claim 17, further comprising: executable code toallow the user to modify the at least one data collection policy for theat least one of the agents.
 19. Computer software, according to claim18, further comprising: executable code that provides the at least onedata collection policy to the at least one agent in response to a usermodifying the at least one data collection policy.
 20. Computersoftware, according to claim 19, further comprising: executable codethat allows a user to delete the at least one data collection policy.21. Computer software, according to claim 18, further comprising:executable code that provides to the at least one agent all of the datacollection policies for the at least one agent in response to a usermodifying the at least one data collection policy.
 22. Computersoftware, according to claim 18, further comprising: executable codethat allows the user to select one or more of the agents to which the atleast one data collection policy is to be applied.
 23. Computersoftware, according to claim 22, further comprising: executable codethat restricts the user to applying the at least one data collectionpolicy to only agents of an appropriate type.
 24. Computer software,according to claim 18, further comprising: executable code thatfacilitates the user modify a template for the at least one datacollection policy.
 25. Computer software, according to claim 15, whereinthe agents include executable code that overrides any of the agents'built-in data collection policies.
 26. Computer software, according toclaim 15, further comprising: executable code for applying each of thedata collection policies to a single agent, a group of agents, or agentsthat service a particular type of object of the storage area network.